Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP v0.5.0-rc.2 #3

Open
wants to merge 109 commits into
base: master
Choose a base branch
from
Open

WIP v0.5.0-rc.2 #3

wants to merge 109 commits into from

Conversation

kolbma
Copy link

@kolbma kolbma commented Jan 19, 2022

This branch is based on the earlier PRs and it is NOT intended for NOW being merged...

Just to follow what is going on...

You can give me in comments some hints for what is ready to be pulled from other PRs!

My intention is to continue with these next steps...

  1. Finish Docker image build for development
  2. Update versions of dependencies and fixing what is needed to be again green on the available tests
  3. Cleanup unused dependencies if the case
  4. Merge a couple of PRs from Sergio's Repo which are for sure useful

2, 3 and 4 in some round-robin fashion.

Always welcome are updates to website and documentation. My mother language is not English and so I would maybe produce some amusement and obscurities. ;-)

Lochlann Andrews and others added 30 commits September 3, 2021 01:03
I don't have an explanation why the rust std print macros panic, but this fixes rwf2#2019

Tested with and without redirecting. Log output looks like usual.
needs secure feature for signed and private cookies
Fixes rwf2#2063

In cookies::CookieJar::get_private_pending() is no decrypt of pending cookie possible, because pending cookies are just operated before server sends response and so cookies are not yet encrypted. Just return the cookie as it is.
Dependency multer -> spin doesn't build below rust 1.51.0 which seems to be related to  
* atomic::spin_loop_hint has been deprecated. It's recommended to use hint::spin_loop instead.
resolving fails below because of crate time
cargo resolving fails below because of crate time
Testing combination of non-private/private cookies and
if private ones get en- and decrypted.
Documentation and Site must be done later.
fix(log): implement print macros without panic
fix: CookieJar::get_private_pending() rwf2#2063
There will be some dep updates
@@ -119,6 +117,7 @@ impl Poolable for diesel::SqliteConnection {
type Error = std::convert::Infallible;

fn pool(db_name: &str, rocket: &Rocket<Build>) -> PoolResult<Self> {
use std::time::Duration;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you moving the use statement?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unused depending on feature compilation

BuildError::Backend(e) => Error::Init(e),
BuildError::NoRuntimeSpecified(e_msg) => {
// it is set above in builder, so panic here
panic!("init failed to set runtime: {}", e_msg)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may result in poor user-experience.
If crashing is the only option - it would be nice to at least explain to the user what is missing and how to fix it.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No it will not because this can only happen if we had forgot to set the runtime above.

* Metadata is pub(crate)
* derive Debug, Clone is at the moment not used
* field query_segs is only written, but not read
* unused cleaned up
* paths changed in output
* compiler messages changed
@somehowchris
Copy link

@kolbma @najtin can we git this work into smaller pieces? Just to make it more digestable, there is cpp code, dockerfiles, config files, bash scripts, ui tests, dependency updates and much more. Though much is needed I dont think one huge move should do it

@somehowchris somehowchris mentioned this pull request Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants